Associating an information reader and a medical device

ABSTRACT

A device agent including an information accessor for accessing association information obtained via an information reader. The association information includes medical device information for uniquely identifying the medical device, and device agent information for facilitating in an association between the medical device and the information reader. The device agent also includes an associator for associating the medical device and the information reader based on the association information.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/404,503, filed Jan. 12, 2017, which is a continuation of U.S. patentapplication Ser. No. 14/733,885 (now issued as U.S. Pat. No. 9,547,751),filed Jun. 8, 2015, which is a continuation of U.S. patent applicationSer. No. 13/275,005 (now issued as U.S. Pat. No. 9,053,520), filed Oct.17, 2011, each entitled “Associating An Information Reader and A MedicalDevice”, the contents of which are herein incorporated by reference intheir entirety.

BACKGROUND

Barcode systems are often used in medical environments to ensure safety.For example, a barcode system can ensure that correct drugs are given tothe proper patient or only authorized personnel can administer theproper medical protocol to a patient.

Oftentimes, a barcode scanner is permanently associated with a singlemedical device. For example, the barcode scanner is physically attachedto the medical device. As a result, the flexibility of a medicalenvironment is limited because it is difficult to share barcode scannerswith other medical devices.

Also, a floating barcode is utilized in BCMA systems. For floatingbarcode devices, barcode scans are sent to a centralized system. Thescanning is only done to get information (e.g., device id, similar towhen you scan a badge), and the information is used in backend systemsto perform some general work. However, the intent and workflow,regarding the floating barcode in a BCMA system, is not for directingsubsequent barcode scans to a particular device.

Moreover, a barcode scanner may be unable to directly communicate with amedical device because of limited communication capabilities.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-3 illustrate embodiments of a medical system.

FIG. 4 illustrates an embodiment of displayed information.

FIG. 5 illustrates an embodiment a method for associating an informationreader and medical device.

The drawings referred to in this description should be understood as notbeing drawn to scale except if specifically noted.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments of the presenttechnology, examples of which are illustrated in the accompanyingdrawings. While the technology will be described in conjunction withvarious embodiment(s), it will be understood that they are not intendedto limit the present technology to these embodiments. On the contrary,the present technology is intended to cover alternatives, modificationsand equivalents, which may be included within the spirit and scope ofthe various embodiments as defined by the appended claims.

Furthermore, in the following description of embodiments, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present technology. However, the present technologymay be practiced without these specific details. In other instances,well known methods, procedures, components, and circuits have not beendescribed in detail as not to unnecessarily obscure aspects of thepresent embodiments.

In general, information readers are associated with medical devices toensure safety in a medical environment. The discussion below willdescribe a variety of means to associate an information reader withmedical device(s). In particular, the discussion will first describe thecomponents in a medical environment. Then the discussion will describefunctionality of the components during use of the medical environment.

It is understood that “association,” as used herein, for example, theassociation between an information reader and a medical device,generally describes the communicative coupling between the devices. As aresult of the association, information, obtained by the informationreader, is able to be routed to the associated device(s).

FIG. 1 depicts an embodiment of medical environment 100. Medicalenvironment 100 includes medical device 110, information reader 130 anddevice agent 140.

Information reader 130 is any device that is capable of readinginformation and also able to be associated with a medical device. Forexample, information reader 130 can be, but is not limited to, a barcodescanner, a radio-frequency identification (RFID) reader. Moreover,information reader 130 can be any device (e.g., a mobile device) withbarcode scanning and/or RFID reading capabilities.

Medical device 110 can be any medical device(s) that is able to beassociated with an information reader. For example, medical device is aventilator, infusion pump, etc.

In general, association information 122 is utilized to facilitate in theassociation between information reader 130 and medical device 110.Association information 122 includes medical device information 124,device agent information 126 and optionally, additional commandinformation 128.

Also, in various embodiments, association information 122 includes acookie (data element) that appends to any consecutive scan after anassociation generated. The cookie allows the destination device (and/orrouting devices) to uniquely identify scans intended for the destinationdevice.

Medical device information 124 includes any information or signaturethat uniquely identifies medical device 110 and/or any other medicaldevices. For example, medical device information 124 can be, but is notlimited to, model number, serial number, Media Access Control address(MAC) address, Internet Protocol (IP) address, etc.

Device agent information 126 includes any information that can beutilized by device agent 140 (or any other device agent) to properlyroute information, obtained by information reader 130, to medical device110. For example, device agent information 126 can include, but is notlimited to, agent name, connectivity parameters (e.g., IP/Bluetoothparameters), commands for routing information to a specific device(e.g., medical device 110), and authentication information.

Additional command information 128 can be any additional information(other than medical device information 124 and device agent information126) that provides commands for routing information obtained byinformation reader 130. For example, additional command information 128can provide commands to device agent 140 to route information to otherdevices. In another example, command information 128 can includedisassociation information (e.g., disassociate immediately, or after Xseconds).

Association information 122 is able to be read or obtained byinformation reader 130 via information device 120. In variousembodiments, information device 120 is a barcode (static or dynamic) oran RFID tag. Accordingly, association information 122 is presented as astatic barcode, a dynamic barcode or an RFID tag. As such, informationreader 130 (e.g., a barcode reader or an RFID reader) is able to read orobtain association information 122 via information device 120.

In one embodiment, information device 120 is attached to medical device110. For instance, a barcode or an RFID tag is physically attached(e.g., adhered) to an infusion pump.

In another embodiment, information device 120 is a display for renderinga scannable barcode. In such an embodiment, association information 122is dynamically displayed on information device 120. Also, the displaycan be integrated within medical device 110 or can be separate, butproximate to, medical device 110. It should be understood that therendered barcode (displayed on the display) contains the associationinformation 122 describe above.

Device agent 140 is an agent or proxy for medical device 110 and isutilized to facilitate in the association between information reader 130and medical device 110. Device agent 140 includes information accessor142, router 144, associator 146, dissassociator 148, and optionally,proximity estimator 149.

Information accessor 142 is for accessing association information 122via information reader 130.

Associator 146 is configured for associating medical device 110 andinformation reader 130 based on association information 122.Disassociator 148 is for disassociating an established associationbetween information reader 130 and medical device 110.

Proximity estimator 146 is for estimating a proximity or distancebetween medical device 110 and information reader 130.

Router 144 is for routing subsequent information (e.g., information froma scanned barcode on a bottle of medicine) to medical device 110.

During use of medical environment 100, information reader 130 andmedical device 110 are initially unassociated. As such, any informationobtained by information reader 130 would not necessarily be routed tomedical device 110.

In order to associate information reader 130 and medical device 110,information reader 130 reads association information 122. In particular,medical device information 124 and device agent information 126. Forexample, a handheld barcode scanner scans a barcode that includes theserial number of medical device 110 and the MAC address for device agent140.

Information reader 130 communicates with device agent 140 in a varietyof ways. In various examples, information reader 130 communicates withdevice agent 140 by Universal Serial Bus (USB), internet, Wi-Fi,Bluetooth, etc.

Information accessor 142 accesses association information 122.Associator 150 obtains association information 122 and associatesinformation reader 130 and medical device 110 based on associationinformation 122. For example, associator 150 generates an associationbased on the received serial number of medical device 110 and the MACaddress for device agent 140.

In one embodiment, associator 146 automatically generates an associationin response to the obtained association information 122. In anotherembodiment, associator 146 automatically generates an association inresponse to user input, which will be described in detail below.

As a result of the generated association, router 144 routes subsequentinformation obtained by information reader 130 to medical device 110.For example, batches of medication are intended to be infused intoPatient A. Barcodes on the batches of medication are scanned byinformation reader 130. The information from the scanned barcodes arethen routed to medical device 110 (e.g., an infusion pump) to facilitatein the infusion of the drugs into Patient A.

In one embodiment, information reader 130 obtains information prior toan established association with medical device 110. For example,information reader 130 obtains information by scanning barcodes onbatches of medicine for Patient A. The information is stored in memory135. Memory 135 can be located within information reader 130 or otherlocations, such as a server, within medical environment 100.

In response to an association between information reader 130 and medicaldevice 110 (established by associator 146), the information (obtainedprior to association) stored in memory 135 is routed to medical device110.

In various embodiments, the association is a logical peer-to-peerassociation between information reader 130 and medical device 110. FIG.1 depicts an association through device agent 140. However, in variousother embodiments, the association can utilize point-to-point radiotechnology on a network (e.g., a local area network (LAN), a wirelessLAN (WLAN), or a personal area network (PAN) (e.g., Bluetooth orZigbee)). In an embodiment of a PAN, direct communication betweeninformation reader 130 and medical device 110 is established withoutrequiring any network infrastructure.

Referring now to FIG. 4 , to enhance safety and control (enabled ordisabled through device configuration) an acknowledgment dialog 400 isdisplayed on user interface 112 of medical device 110.

A user is prompted to accept the attempted association. If the userchooses to deny the association attempt, medical device 110 will notaccept subsequent information (e.g., subsequent barcode scans) frominformation reader 130, unless a new authentication is performed andaccepted.

Referring again to FIG. 1 , disassociator 148 terminates ordisassociates the association between information reader 130 and medicaldevice 110. In order to reduce the likelihood of undesired informationto be routed to a medical device, provisions are added to limit theduration that the association is effective.

For example, a disassociation of an information reader from a medicaldevice can be accomplished via a user interface of the informationreader and/or medical device.

Disassociation can automatically occur after a pre-determined amount oftime from association. For example, a disassociation automaticallyoccurs after four hour from the time of association.

Disassociation can occur after a pre-determined amount of time from thelast scan. For example, a disassociation automatically occurs after onehour from the last scan of the information reader.

Disassociation can occur in response to the devices exceeding apre-determined maximum distance. For example, proximity estimator 149estimates the proximity between information reader 130 and medicaldevice 110. In response to medical device 110 and information reader 130exceeding a pre-determined maximum distance (e.g., 40 feet), medicaldevice 110 and information reader 130 are disassociated.

Disassociation can automatically occur in response if a connection(e.g., wireless) between the devices is lost.

Disassociation can automatically occur in response to completed workflow. For example, disassociation occurs after successful drug scanning,and patient ID and/or clinician ID are associated with the medicaldevice.

Disassociation can occur if information reader reads/obtains associationinformation of another medical device.

Referring to FIG. 2 , medical environment 200 includes network 205,wireless access points 207 and 208, device agents 140 and 240,information reader 130, and medical devices 110 and 210.

Medical device 110 also includes wireless module 214. Wireless module214 allows for medical device 110 to wirelessly connect to network 205via wireless access points 207 and/or 208.

Also, medical device 110 is connected to or associated with othermedical devices, such as medical device 210. For example, medical device110 is a first Large Volume Parenterals (LVP) device and medical device210 is a second LVP device.

Moreover, medical device 210 does not have the capability to directlycommunicate with information reader 130. Although two medical devicesare depicted in FIG. 2 , it should be appreciated that any number ofmedical devices can be connected to or associated with one another.

During use of medical environment 200, information reader 130 can beassociated with medical device 110 in the same manner as describedabove.

In one embodiment, information 130 can also be associated with medicaldevice 210. In order to associate information reader 130 and medicaldevice 210, information reader 130 reads association information 122which is presented by medical device 110. In particular, informationreader 130 reads medical device information 124 which uniquelyidentifies medical device 210.

Information accessor 142 accesses association information 122.Associator 150 obtains association information 122 and subsequentlyassociates information reader 130 and medical device 210 based onassociation information 122. As a result of the generated association,router 144 routes subsequent information obtained by information reader130 to medical device 210.

It should be appreciated that information reader 130 can be concurrentlyassociated with medical devices 110 and 210.

It may be desired that medical devices 110 and 210 are to utilize deviceagent 240 rather than device agent 140. For example, medical devices 110and 210 initially utilize device agent 140. However, for purposes oftesting the medical devices, device agent 240 (e.g., a testing deviceagent) is utilized.

Accordingly, information reader 130 reads association information 122.In particular, information reader 130 reads device agent information 126which identifies device agent 240. As a result, subsequent informationobtained by information reader 130 is routed to medical device 110and/or 210 via router 240 (rather than device agent 140).

A device agent (e.g., device agent 140) can optionally add functionalityto the system. The device agent can be a physical device or virtualdevice agent, which has close communication with the medical devices.The device agent can manage the scan workflows and rules such as validscan, valid sequence of scans, association and disassociation ofbarcode. A valid scan can include valid data in the scan, a scansupported by a medical device such as intermittent infusion or PCAinfusion not supported by the device. A valid sequence may includescanning patient ID, clinical ID and a drug scan.

A device agent can determine when to associate the barcode and when todisassociate the barcode. A device agent may perform preprocessing ofthe scan before sending to medical device such as mapping the drug entryID to drug name or order ID to order details. In this case, the deviceagent will store drug library and order information.

Referring to FIG. 3 , an embodiment of medical environment 300 isdepicted. Medical environment 300 includes information reader 130 andmedical devices 110, 310 and 312.

In such an embodiment, medical device 110 includes device agent 140. Inother words, medical device 110 also functions as device agent 140. Forexample, medical device 110, 310 and 312 are devices in a medical devicerack system. As such, medical device 110 acts as a proxy or device agentfor medical devices 311 and 312 because medical devices 311 and 312 donot have the capability to directly communicate with information reader130.

During use of medical environment 300, information reader 130 can beassociated with medical device 310 in the same manner as describedabove.

In another embodiment, information 130 can also be associated withmedical devices 311 and 312. In order to associate information reader130 and medical devices 311 and/or 312, information reader 130 readsassociation information 122 which is presented by medical device 310. Inparticular, information reader 130 reads medical device information 124which uniquely identifies medical devices 311 and/or 312.

Information accessor 142 accesses association information 122.Associator 150 obtains association information 122 and subsequentlyassociates information reader 130 and medical devices 311 and/or 312based on association information 122. As a result of the generatedassociation, router 144 routes subsequent information obtained byinformation reader 130 to medical devices 311 and/or 312.

FIG. 5 depicts an embodiment of a method 500 for associating aninformation reader and a medical device. In various embodiments, method500 is carried out by processors and electrical components under thecontrol of computer readable and computer executable instructions. Thecomputer readable and computer executable instructions reside, forexample, in a data storage medium such as computer usable volatile andnon-volatile memory. However, the computer readable and computerexecutable instructions may reside in any type of computer readablestorage medium. In some embodiments, method 500 is performed at least bydevice agent 140 and/or medical device 110, as depicted in FIG. 1 .

At 510 of method 500, association information is accessed via theinformation reader, wherein the information comprises medical deviceinformation for uniquely identifying the medical device, and deviceagent information for facilitating in an association between the medicaldevice and the information reader.

For example, association information 122 is scanned by informationreader 130 (e.g., barcode scanner). In particular, associationinformation 122 includes medical device information 124 which is aunique signature of medical device 110 and device agent information 126which can include agent name, connectivity parameters (e.g.,IP/Bluetooth parameters), and/or commands for routing information to aspecific device.

In one embodiment, at 512, association information displayed proximatethe medical device is accessed. For example, association information 122is presented by information device 120 (e.g., dynamic barcode) which isphysically attached to medical device 110.

At 520, the medical device and the information reader are associatedbased on the association information. For example, associator 146associates information reader 130 and medical device 110 based onassociation information 122.

At 530, a proximity is estimated between the medical device and theinformation reader. For example, information reader 130 and medicaldevice 110 are disassociated in response to the devices exceeding amaximum distance. It should be understood that the proximity estimationutilized for disassociation is just one embodiment for managingdisassociation. In particular, the proximity estimation is not requiredin all embodiments.

At 540, subsequent information obtained via the information reader isrouted to the medical device. For example, router 144 routes informationobtained by scanning barcodes on batches of medicine to medical device110.

At 550, subsequent information obtained via the information reader isrouted to another medical device, wherein the another medical device isassociated with the medical device. For example, router 144 routesinformation obtained by scanning barcodes on batches of medicine tomedical devices 311 and/or 312.

At 560, in response to the association, route previously obtainedinformation to the medical device. For example, prior to association,information reader 130 obtains information and the information is storedin memory 135. In response associator 146 establishing an associationbetween information reader 130 and medical device 110, the informationstored in memory 135 is routed to medical device 110.

At 570, a disassociation occurs between the medical device and theinformation reader. For example, disassociation occurs in response to alost wireless connection between medical device 110 and informationreader 130.

Various embodiments of the present invention are thus described. Whilethe present invention has been described in particular embodiments, itshould be appreciated that the present invention should not be construedas limited by such embodiments, but rather construed according to thefollowing claims.

1-20. (canceled)
 21. An infusion pump for medication infusion within amedical environment comprising: a display; a wireless module configuredto communicate with a wireless network; at least one data processor; andat least one memory including computer program code, the at least onememory and the computer program code configured to, with the at leastone data processor, cause the infusion pump to at least: render ascannable tag on the display of the infusion pump, wherein the scannabletag is configured to be scanned by an information reader to at leastconfigure the infusion pump for receiving medication informationsubsequently routed to the infusion pump, wherein the information readeris at least one of an optical scanner and a mobile device with opticalscanning capabilities; receive medication information about medicationto be administered to the patient after the information reader scans thescannable tag and after the information reader scans a medicationbarcode on the medication, the medication information including at leastone of an infusion parameter of the medication, a medication name, or amedication order identifier; and operate, based at least on the receivedmedication information, to cause administration of an infusion of themedication.
 22. The infusion pump of claim 21, wherein the infusion pumpis configured to communicatively couple with the information reader. 23.The infusion pump of claim 22, wherein the at least one memory and thecomputer program code are configured to, with the at least one dataprocessor, cause the infusion pump to associate with the informationreader after the infusion pump is communicatively coupled with theinformation reader.
 24. The infusion pump of claim 22, wherein the atleast one memory and the computer program code are configured to, withthe at least one data processor, cause the infusion pump to associatewith the information reader before the infusion pump is communicativelycoupled with the information reader.
 25. The infusion pump of claim 21,wherein the at least one memory and the computer program code arefurther configured to, with the at least one data processor, cause theinfusion pump to receive patient information identifying a patient afterthe information reader scans a patient identifier.
 26. The infusion pumpof claim 21, wherein the at least one memory and the computer programcode are further configured to, with the at least one data processor,cause the infusion pump to receive clinical information identifying aclinician after the information reader scans a clinical identifier. 27.The infusion pump of claim 21, wherein the at least one memory and thecomputer program code are further configured to, with the at least onedata processor, cause the infusion pump to: store the medicationinformation in the at least one memory of the infusion pump; and render,on the display, at least a portion of the medication information. 28.The infusion pump of claim 21, wherein the scannable tag furthercomprises routing information defining parameters for routing themedication information to the infusion pump.
 29. The infusion pump ofclaim 28, wherein the routing information comprises at least one of:connectivity parameters of the infusion pump or authenticationinformation of the infusion pump.
 30. The infusion pump of claim 21,wherein the scannable tag further comprises disassociation informationdefining one or more parameters for disassociating the infusion pump andthe information reader, and wherein the at least one memory and thecomputer program code are further configured to, with the at least onedata processor, cause the infusion pump to disassociate from theinformation reader after at least one parameter of the one or moreparameters is satisfied.
 31. The infusion pump of claim 21, wherein thescannable tag comprises a barcode.
 32. The infusion pump of claim 21,wherein the at least one memory and the computer program code arefurther configured to, with the at least one data processor, cause theinfusion pump to: connect to the wireless network; receive, from aserver connected to the communication network and after scanning of thescannable tag, a request for communicative coupling with the infusionpump; and render, on the display, a dialog to acknowledge the request.33. An infusion system for medication infusion within a medicalenvironment comprising: a display; a wireless module configured tocommunicate with a wireless network; at least one data processor; and atleast one memory including computer program code, the at least onememory and the computer program code configured to, with the at leastone data processor, cause the infusion system to at least: render ascannable tag on the display, wherein the scannable tag is configured tobe scanned by an information reader to at least configure the infusionsystem for receiving medication information subsequently routed to theinfusion system, wherein the information reader is at least one of anoptical scanner and a mobile device with optical scanning capabilities;communicatively couple with the information reader; receive medicationinformation about medication to be administered to the patient after theinformation reader scans the scannable tag, communicatively couples withthe information reader, and the information reader scans a medicationbarcode on the medication, the medication information including at leastone of an infusion parameter of the medication, a medication name, or amedication order identifier; and cause, based at least on the receivedmedication information, administration of an infusion of the medication.34. The infusion system of claim 33, wherein the scannable tag comprisesa barcode.
 35. The infusion system of claim 33, wherein the scannabletag comprises routing information defining parameters for routing themedication information to the infusion system.
 36. The infusion systemof claim 35, wherein the at least one memory and the computer programcode are further configured to, with the at least one data processor,cause the infusion system to transmit the routing information to arouter within the medical environment.
 37. The infusion system of claim33, wherein the at least one memory and the computer program code arefurther configured to, with the at least one data processor, cause theinfusion pump to: store the medication information in the at least onememory; and render, on the display, at least a portion of the medicationinformation.
 38. The infusion system of claim 34, wherein the at leastone memory and the computer program code are further configured to, withthe at least one data processor, cause the infusion system to receivesecond medication information about a second medication to beadministered to the patient by the infusion system, the secondmedication information including at least one of: infusion parameters ofthe second medication, a second medication name, or a second medicationorder identifier.
 39. The infusion system of claim 38, wherein the atleast one memory and the computer program code are further configuredto, with the at least one data processor, cause the infusion system toreceive the second medication information obtained by the informationreader after the infusion system is communicatively coupled with theinformation reader.
 40. The infusion system of claim 33, wherein the atleast one memory and the computer program code are further configuredto, with the at least one data processor, cause the infusion system to:receive at least one of patient information identifying a patient orclinical information identifying a clinician, wherein the at least onememory and the computer program code are further configured to, with theat least one data processor, cause the infusion system to receive the atleast one of the patient information or the clinical information routedto the infusion system after the information reader scans the at leastone of the patient information or the clinical information.